-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SwipeableDrawer] Remove internal accesses in the tests #15469
[SwipeableDrawer] Remove internal accesses in the tests #15469
Conversation
joshwooding
commented
Apr 23, 2019
- I have followed (at least) the PR section of the contributing guide.
@material-ui/core: parsed: -0.42% 😍, gzip: -0.23% 😍 Details of bundle changes.Comparing: 4516caf...de92e06
|
b1b716e
to
88afeb0
Compare
e06a006
to
c800aa0
Compare
Removed setting styles via useEffect. It's a nice to have but the work needed to get it working might be substantial |
c800aa0
to
e14a553
Compare
@@ -416,7 +416,6 @@ const SwipeableDrawer = React.forwardRef(function SwipeableDrawer(props, ref) { | |||
}} | |||
anchor={anchor} | |||
transitionDuration={transitionDuration} | |||
hideBackdrop={hideBackdrop} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, it looks like this is passed through in the old version but when variant="permanent" it gets passed to a div.
dc7fabe
to
6a49299
Compare
Looks like the last test failing is an actual failure. Edit: Fixed using a ref |
Details of bundle changes.Comparing: 1555e52...fa4d8c0
|
Not entirely sure on how to continue with this :/ I have no way of determining why it fails on Chrome v41 on OS X |
@joshwooding Let me know if you want some creds to access BrowserStack, in the meantime. Let's see if I can help here :). |
529399e
to
a02c4c3
Compare
a02c4c3
to
be73565
Compare
@joshwooding I have reverted the component changes to focus on the test changes. The build is green now. I think that moving away from internal tests in already very valuable.
Once the test changes are merged, we can move forward with the implementation :). |
@joshwooding Given that we already have the context fresh in our memory for the migration of this component, what do you think about completing the migration before starting another effort? I was about to say that we could delay it but we will lose some context if we handle it in the future. |
@oliviertassinari Sure :) As always the tests are the hardest part of nearly all of the migrations. Hopefully now we have done the tests the actually migration should be easy 🤞 |